Repository navigation
Switch to calendar versioning: YY.N[.P] - #718
Merged
Merged
Conversation
Releases are now numbered YY.N, with N counting the releases within the year from 0, and YY.N.P for patch releases; the prerelease id is unchanged. Since 2.1.0 and 2.2.0 already shipped in 2026, the next release is 26.2 and master now reports 26.2-alpha. The version components are SEQUANT_YEAR_VERSION, SEQUANT_YMAJOR_VERSION and SEQUANT_PATCH_VERSION instead of MAJOR/MINOR/MICRO, since "minor" no longer implies API stability. A zero patch level is omitted from SEQUANT_VERSION, the installed package config and the share directory. Downstream find_package(SeQuant 2.x) requests still succeed under the AnyNewerVersion compatibility policy.
ajay-mk
reviewed
Oct 21, 2026
Collaborator
|
I would favor using |
Member
Author
I am running a poll. I prefer YY to avoid redundant 20. |
Member
Author
|
@Krzmbrzl majority seemed to prefer 26.2 . YY works for Ubuntu, MacOS, LibreOffice, pip, etc. |
Collaborator
|
Alright. We should add s note about the use of CalVer to the README to make sure there is no ambiguity |
Krzmbrzl
approved these changes
Oct 22, 2026
ajay-mk
approved these changes
Oct 22, 2026
…oning The scheme was only described in the maintainer release guide; users looking at the README or the installation page had no way to tell that 26.2 is a calendar version rather than a semver major bump.
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Switches SeQuant from semantic to calendar versioning. Releases are numbered
YY.N, whereNcounts the releases within the year starting from 0, and patch releasesYY.N.P; the prerelease id (-alphaetc.) is unchanged. Since 2.1.0 and 2.2.0 already shipped in 2026, the next release is 26.2, and master now reports26.2-alpha.Changes:
CMakeLists.txt: version components are nowSEQUANT_YEAR_VERSION,SEQUANT_YMAJOR_VERSION,SEQUANT_PATCH_VERSION(replacing MAJOR/MINOR/MICRO, since "minor" no longer implies API stability). A zero patch level is omitted fromSEQUANT_VERSION; the share directory uses the same string.SeQuant/version.hpp.in,cmake/sequant-config.cmake.in: macros and comments follow the new scheme.CITATION.cff:26.2-alpha.doc/maintainer/release.rst: version numbering section rewritten for calver; checklist usesvYY.N.xbranches andvYY.N/vYY.N.Ptags, and spells out the post-release bump across a year boundary.Verified: the generated
sequant-config-version.cmakeacceptsfind_package(SeQuant 2.0),2.3,26.2,26.2.0and rejects26.3,27.0underAnyNewerVersion; a patch level of 1 yields26.2.1. Nothing in SeQuant or MPQC used the old macro names.